The Juniper router must be configured to generate log records for DoD-defined auditable events.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-91111	JUNI-ND-000230	SV-101211r1_rule		Medium

Description
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., process, module). Certain specific device functionalities may be audited as well. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. DoD has defined the list of events for which the device will provide an audit record generation capability as the following: (i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); (ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; and (iii) All account creation, modification, disabling, and termination actions.

Description

Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., process, module). Certain specific device functionalities may be audited as well. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records. DoD has defined the list of events for which the device will provide an audit record generation capability as the following: (i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels); (ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; and (iii) All account creation, modification, disabling, and termination actions.

STIG	Date
Juniper Router NDM Security Technical Implementation Guide	2019-07-01

Details

Check Text ( C-90265r2_chk )
Review the router configuration to verify that it is compliant with this requirement. The configuration example below various types of events to be logged. syslog { file LOG_FILE { authorization info; security info; firewall info; change-log info; } } Note: The parameter "any" can be in place of configuring specific events as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below. system { syslog { host 10.1.58.2 { any info; } } } If the router is not configured to generate log records for DoD-defined auditable events, this is a finding.

Check Text ( C-90265r2_chk )

Review the router configuration to verify that it is compliant with this requirement. The configuration example below various types of events to be logged.

syslog {
file LOG_FILE {
authorization info;
security info;
firewall info;
change-log info;
}
}

Note: The parameter "any" can be in place of configuring specific events as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

system {
syslog {
host 10.1.58.2 {
any info;
}
}
}
If the router is not configured to generate log records for DoD-defined auditable events, this is a finding.

Fix Text (F-97309r2_fix)
Configure the router to generate log records for DoD-defined auditable events as shown in the configuration example below. [edit system] set syslog file LOG_FILE authorization info set syslog file LOG_FILE security info set syslog file LOG_FILE firewall info set syslog file LOG_FILE change-log info Note: The parameter "any" can be in place of configuring specific events as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below. set syslog host 10.1.58.2 any info

Fix Text (F-97309r2_fix)

Configure the router to generate log records for DoD-defined auditable events as shown in the configuration example below.

[edit system]
set syslog file LOG_FILE authorization info
set syslog file LOG_FILE security info
set syslog file LOG_FILE firewall info
set syslog file LOG_FILE change-log info

Note: The parameter "any" can be in place of configuring specific events as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

set syslog host 10.1.58.2 any info